@JaredBusch said in Taking over IT for a small business:

@scottalanmiller said in Taking over IT for a small business:

@JaredBusch said in Taking over IT for a small business:

@scottalanmiller said in Taking over IT for a small business:

@Dashrender said in Taking over IT for a small business:

LOL - If I were the boss, I could do that. She has already ordered me to remove her from the monthly updates - so I have to nag her to do those manually, they can't be pushed to her via WSUS, because of reboots.

Make sure you have a "get it in writing to remove HIPAA requirement automation."

OH, good one.. She's breaking HIPAA by not being updated.

Over a certain time frame, yeah. 🙂 That's going to be the big motivation here. Maybe he should even go to the owners and say "as you title me an IT decision maker, I meed a sign off to allow disregarding the law and a statement that I'm not allowed to follow HIPAA against my requirements, knowledge, and recommendations." Don't argue it, just make them state that they've accepted responsibility by demanding he not follow HIPAA.

But since automatic is disabled, he has no insight to know the time frame is being kept. So yeah.

Right, even if she promises to do it as HIPAA requires, he needs to be indemnified from that.

@wrx7m said in Windows 10 Updates - Trigger "Update and Restart":

@IRJ said in Windows 10 Updates - Trigger "Update and Restart":

@wrx7m said in Windows 10 Updates - Trigger "Update and Restart":

@IRJ said in Windows 10 Updates - Trigger "Update and Restart":

@wrx7m said in Windows 10 Updates - Trigger "Update and Restart":

A simple restart command doesn't perform the update step, just the restart, so the update doesn't get applied.

This has been an issue for a very long time with windows. I am surprised it hasn't been fixed yet. It's really annoying

Well, at least with Win 7, a standard reboot applies updates. At least, I think it does. The main difference between Win 7 and 10, is that they have switched to the osoclient.exe to manage the updates.

I'm pretty sure server 2008 and onward had the issue. I don't remember dealing with it on workstations

I still have a 2008 R2 box and can test it on the next go 'round. I won't have it much longer, as I am dumping it prior to EOS.

LOL - Didn't make this cutoff. Next week, hopefully.

Instead of contacting support, have you tried the Bill & Melinda Gates Foundation along with viewers like you?

Ok, so junction points don't support mapping to network path, symlinks do, and hardlinks can only be created for files, not folders. Try creating symlink and then create junction to the symlink and see if Crashplan can be fooled that way. So mklink /D C:\fake-Backup \\server01\Share\Subfolder and mklink /J c:\backup c:\fake-backup .

Within PowerShell can't use something like Push-Location \\Server\Share\path or Set-Location \\Server\Share\path and then run the cipher command?

Can you post the result of these two reg queries:

REG QUERY HKLM\Software\Microsoft\Windows\CurrentVersion\Policies\System\ /v ConsentPromptBehaviorAdmin REG QUERY HKLM\Software\Microsoft\Windows\CurrentVersion\Policies\System\ /v ConsentPromptBehaviorUser

I won't have any Win 7 systems by that time. At least that is the goal. I was thinking it was Jan 20, 2020. Guess I just confabulated that based on the year being 2020. Still have about 40 systems to issue to replace them.

@scottalanmiller said in Joining 2 Windows 10 Machines:

@DustinB3403 said in Joining 2 Windows 10 Machines:

How would he even license this?

As long as one of the Windows 10 copies is retail rather than OEM or he gets two OEMs for the same hardware...

Right there is basically no issue here. WTF with this thread.

@JaredBusch said in SSH Access to Windows 10 Pro Workstations:

@DustinB3403 said in SSH Access to Windows 10 Pro Workstations:

@scottalanmiller said in SSH Access to Windows 10 Pro Workstations:

On Server, no issue. SSH the same as with Linux. SSH on Windows 10 is "single user" just like anything else on Windows 10.

So then why would they have the statement about "usually to correct problems" as to me this would be a two person use. One who is using the desktop and the other administrator who is working on fixing an issue via ssh (presumably while the other user is using said system).

I'm not bothering to reread anything, but MS has long allowed admin connections.

Yes this has been a known fact for as long as i can remember... Admins are exempt for administrative purposes.

@scottalanmiller said in Windows 10 PC's not renewing DHCP lease:

@Dashrender said in Windows 10 PC's not renewing DHCP lease:

@scottalanmiller said in Windows 10 PC's not renewing DHCP lease:

@Dashrender said in Windows 10 PC's not renewing DHCP lease:

@dafyre said in Windows 10 PC's not renewing DHCP lease:

Your DHCP range isn't close to being full, is it?

Man, I wouldn't think that would prevent a renewal.

It does. Depends on race conditions, but it definitely happens.

I guess I need to re-read up on the DHCP process - I thought (at least with Windows) that the client machine did a check at the 50% timeframe and renewed then, thereby never actually reaching an expired state. But that was 20+ years ago when I read the MS docs on it... so I could have a faulty memory.

It does, but machines powering on and off and such can disrupt that process.

uh, what? Sure, now if a machine is off, and the half way point, or the full expire time hits, sure, when the machine comes back online - it has to basically start over...

The OP says the machine is loosing it's IP what appears to be overnight. OK, so let's assume the lease expired while the computers were in powersaver mode, or simply off. I would expect them to be turned on and simply go through a DHCP request - but the OP says a reboot it required to get back on the network. so something isn't working from the client side.

So the NIC has been updated and that didn't solve it.

Any chance the switch could be the culprit? Are there updates available for the switch?

@scottalanmiller said in Why Microsoft Wants You to Think Windows 7 Can't Be Upgraded:

@Carnival-Boy said in Why Microsoft Wants You to Think Windows 7 Can't Be Upgraded:

Desktop OS is important, because you need a desktop to access the cloud - but it's only important in as much as it is used to sell Azure.

But you can access Azure just as well (or better in many cases) from Ubuntu, ChromeOS, Fedora, macOS, etc.

Of course, but you can push users towards Azure by controlling what users see on the desktop - think pre-installing Skype or Edge or the Microsoft App Store. Google do the same for their OS. Amazon are probably the most explicit in practically giving away Amazon Fires just to push Amazon services.

@JasGot said in Free Upgrade to Windows 10 in 2019 from Windows 7 and Windows 8.1:

@scottalanmiller said in Free Upgrade to Windows 10 in 2019 from Windows 7 and Windows 8.1:

Two weeks left for those trying to go from Windows 7 to Windows 10. The Free Upgrade depends on the OS being current, remember.

Do you think those people who have not upgraded by the 14th will be UNABLE to install and activate from their Windows 7 or 8.1 key?

Notice how I didn't ask about any licensing issues. I already know that answer. 🙂

Likely the ability to upgrade won't change, if there was time/date detection, we'd already have heard about it.

@scottalanmiller said in Why the Windows 10 EULA Is Applicable to Older Windows Licenses:

It then points out that the EULA is not valid only in the case where the source license is not genuine, so like a pirated copy of Windows 8. This entire portion of the EULA is exclusively for the purpose of Windows 7, 8, and 8.1. It has no purpose otherwise.

It does. It also applies when you are installing a clean install of a previously legally licensed Windows 10 system.

@marcinozga said in Any Way to Automate Adding a New Computer to an AD Group?:

@flaxking said in Any Way to Automate Adding a New Computer to an AD Group?:

@marcinozga said in Any Way to Automate Adding a New Computer to an AD Group?:

Ansible can do that. https://docs.ansible.com/ansible/latest/modules/win_domain_group_membership_module.html#win-domain-group-membership-module
You can add new PCs to domain, and change their group membership, you just need to know computer names in advance.

Which is just a layer on top of Powershell. The Active Directory Powershell module is still required.

It's not required, or that module is included already in Windows 10 by default. Because I haven't had to install it on any machine I managed with Ansible.

"win_domain_group_membership requires the ActiveDirectory PS module to be installed"
https://github.com/ansible/ansible/blob/devel/lib/ansible/modules/windows/win_domain_group_membership.ps1

They have it in the documentation as well "This must be run on a host that has the ActiveDirectory powershell module installed."
https://docs.ansible.com/ansible/latest/modules/win_domain_group_module.html

Thanks @black3dynamite .... before I saw that I tried a fresh install (over the top of the old one) and that fixed it for me.

@jt1001001 Thanks. If you are running from PDQ deploy, you won't see anything. But, if you are doing it from PS/ISE or similar, that would be a great help.

Of course it was still broken today - well, the display portion was at least.

While continuing to work on this, since I could see the Manage box, I decided to try to tab to it, and it worked. I pressed enter with it highlighted and I was able to manage it.

Now my goal was to set it as default, the set as default button was missing. After some searching around, I realized that the "Let Windows manage my default printer" box had become rechecked. After unchecking it, and once again using the tab trick to get into manage the MS Print to PDF feature, I was able to set it as the default printer.

So I've found a work-a-round, but the display issue is still there so I don't consider the issue resolved.

@DustinB3403 said in Ads in Windows 10:

@Curtis said in Ads in Windows 10:

@Dashrender We are having this issue now too. What did you decide to do?

I believe he disabled just the individual source of the notifications. In this case the Chrome notifications from the shady websites.

Yep, that's what I did - disabled the specific website that the user had allowed to notify.

@gjacobse said in Yet another Windows 10 File Sharing issue.:

@WrCombs said in Yet another Windows 10 File Sharing issue.:

@WrCombs said in Yet another Windows 10 File Sharing issue.:

@gjacobse said in Yet another Windows 10 File Sharing issue.:

Damn - I was hoping this would fix my issues with access the NAS from the Desktop. Other Windows 10 works fine. Just this one. Previous threads on the matter...

https://mangolassi.it/topic/19632/folder-sharing-issue/76

All I know is one of these fixed it - .

HKLM\system\current control set\services\CSC\ start = 0

HKLM\System\Current Control Set\Services\NetBT\Parameters\UseNewSMB set to 0

Uninstalling reinstalling NIC

Un/installing the NIC allows access via IP,.. more than I had previous. I'll try that the first time the next time it happens.

Thanks.

I do what I can.